Wireless communication network communications through session communication proxies

ABSTRACT

Session Communication Proxies (SCPs) generate SCP status information and/or SCP location information. A source network function selects one of the SCPs based on the SCP status information and/or the SCP location information. The source network function transfers data to the selected one of the SCPs. The selected one of the SCPs receives the data, selects a target network function, and transfers the data to the target network function. In some examples, a Network Repository Function (NRF) prioritizes the SCPs based on the SCP status information and/or the SCP location information, and the source network function selects the one of the SCPs based on the SCP prioritization.

RELATED CASES

This United States Patent Application is a continuation of U.S. patentapplication Ser. No. 17/239,212 that was filed on Apr. 23, 2021 and isentitled “WIRELESS COMMUNICATION NETWORK COMMUNICATIONS THROUGH SESSIONCOMMUNICATION PROXIES.” U.S. patent application Ser. No. 17/239,212 ishereby incorporated by reference into this United States PatentApplication.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless communicationnetworks have Radio Access Networks (RANs) which exchange wirelesssignals with the wireless user devices over radio frequency bands. Thewireless signals use wireless network protocols like Fifth GenerationNew Radio (SGNR), Long Term Evolution (LTE), Institute of Electrical andElectronic Engineers (IEEE) 802.11 (WIFI), and Low-Power Wide AreaNetwork (LP-WAN). The RANs exchange network signaling and user data withnetwork elements that are often clustered together into wireless networkcores. The RANs are connected to the wireless network cores overbackhaul data links.

The RANs comprise Radio Units (RUs), Distributed Units (DUs) andCentralized Units (CUs). The RUs are mounted at elevation and haveantennas, modulators, signal processor, and the like. The RUs areconnected to the DUs which are usually nearby network computers. The DUsare connected to the CUs which are larger computer centers that arecloser to the network cores. The CUs are coupled to network functionsand network elements in the network cores. The network cores execute thenetwork functions and network elements to provide wireless data servicesto the wireless user devices over the RANs. Exemplary network functionsand network elements include Access and Mobility Management Functions(AMFs), Unified Data Managements (UDMs), Session Communication Proxies(SCPs), and Network Repository Functions (NRFs).

In a wireless network core, the network elements use the NRFs toregister themselves and discover other network elements. For example, aUDM registers with an NRF, and an AMF accesses the NRF to discover theUDM. In some examples, the NRF returns an SCP in response to a discoveryrequest. The SCP facilitates indirect communications between networkelement types. A network element may communicate with network elementsof a given type by communicating through the SCP. Unfortunately, the NRFdoes not effectively select SCPs for network elements. Moreover, theNRFs do not efficiently enable the network elements to intelligentlyselect SCPs.

TECHNICAL OVERVIEW

In some examples, Session Communication Proxies (SCPs) generate SCPstatus information. A source network function selects one of the SCPsbased on the SCP status information. The source network functiontransfers data to the selected one of the SCPs. The selected one of theSCPs receives the data, selects a target network function, and transfersthe data to the target network function.

In some examples, SCPs generate SCP location information. A sourcenetwork function selects one of the SCPs based on the SCP locationinformation. The source network function transfers data to the selectedone of the SCPs. The selected one of the SCPs receives the data, selectsa target network function, and transfers the data to the target networkfunction.

In some examples, SCPs generate SCP status information and SCP locationinformation. A source network function selects one of the SCPs based onthe SCP status information and the SCP location information. The sourcenetwork function transfers data to the selected one of the SCPs. Theselected one of the SCPs receives the data, selects a target networkfunction, and transfers the data to the target network function.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network to exchange datacommunications over Session Communication Proxies (SCPs).

FIG. 2 illustrates an exemplary operation of the wireless communicationnetwork to exchange data communications over SCPs.

FIG. 3 illustrates another exemplary operation of the wirelesscommunication network to exchange data communications over SCPs.

FIG. 4 illustrates a Fifth Generation (5G) communication network toexchange data communications over SCPs.

FIG. 5 illustrates Network Function Virtualization Infrastructures(NFVIs) in the 5G communication network.

FIG. 6 further illustrates the NFVIs in the 5G communication network.

FIG. 7 illustrates NRFs and SCPs in the 5G communication network.

FIG. 8 illustrates an exemplary operation of the 5G communicationnetwork to exchange data communications over SCPs.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 to exchange datacommunications through Session Communication Proxies (SCPs) 126.Wireless communication network 100 delivers services to wireless userdevices like internet-access, machine communications, media-streaming,or some other wireless communications product. Wireless communicationnetwork 100 comprises Network Functions (NFs) 121-124, NetworkRepository Function (NRF) 125, and SCPs 126.

Various examples of network operation and configuration are describedherein. In some examples, SCPs 126 determine their location informationand status data. SCPs 126 transfer their location information and statusto NRF 125. NRF 125 prioritizes SCPs 126 based on the locationinformation and the status data. For example, NRF 125 may characterizeindividual ones of SCPs 126 by load and location. NF 121 transfers an NFrequest to NRF 125. NRF 125 receives the NF request from NF 125. Inresponse, NRF 125 generates and transfers a list that prioritizes SCPs126 based on the location information and the status data to NF 121. NF121 responsively selects one of SCPs 126 based on the locationinformation and the status data. For example, NF 121 may select one ofSCPs 126 that is geographically proximate and lightly loaded. NF 121transfers NF data to the selected one of SCPs 126. The selected one ofSCPs 126 receives the NF data and forwards the NF data to NF 123.Advantageously, NRF 125 effectively selects SCPs 126 for NFs 121-124.Moreover, NRF 125 efficiently enables NFs 121-124 to intelligentlyselect SCPs 126.

The wireless user devices and wireless access points illustrated in FIG.1 communicate over links using wireless technologies like FifthGeneration New Radio (SGNR), Long Term Evolution (LTE), Low-Power WideArea Network (LP-WAN), Institute of Electrical and Electronic Engineers(IEEE) 802.11 (WIFI), Bluetooth, and/or some other type of wirelessnetworking protocol. The wireless technologies use electromagneticfrequencies in the low-band, mid-band, high-band, or some other portionof the electromagnetic spectrum. The wireless access points and NFs121-126 communicate over various links that use metallic links, glassfibers, radio channels, or some other communication media. The links useFifth Generation Core (5GC), IEEE 802.3 (Ethernet), Time DivisionMultiplex (TDM), Data Over Cable System Interface Specification(DOCSIS), Internet Protocol (IP), General Packet Radio Service TransferProtocol (GTP), SGNR, LTE, WIFI, virtual switching, inter-processorcommunication, bus interfaces, and/or some other data communicationprotocols.

The wireless user devices comprise computers, phones, vehicles, sensors,robots, or other types of data appliance with wireless and/or wirelinecommunication circuitry. The wireless access points are depicted astowers, but the wireless access points may use other mounting structuresor no mounting structures at all. The wireless access points compriseFifth Generation (5G) Radio Access Networks (RANs), LTE RANs, gNodeBs,eNodeBs, NB-IoT access nodes, LP-WAN base stations, wireless relays,WIFI hotspots, ENET access nodes, Bluetooth access nodes, and/or someother type of wireless or wireline network transceiver. The wirelessuser devices and the wireless access points comprise antennas,amplifiers, filters, modulation, analog/digital interfaces,microprocessors, software, memories, transceivers, bus circuitry, andthe like. NFs 121-124 comprise network functions like Access andMobility Management functions (AMFs), Session Management Functions(SMFs), User Plane Functions (UPFs), and the like. The wireless accesspoints and NFs 121-126 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein.

FIG. 2 illustrates an exemplary operation of wireless communicationnetwork 100 to exchange data communications through SCPs 126. Theoperation may vary in other examples. SCPs 126 determine and transferlocation information and status data to NRF 125 (201). NRF 125 receivesthe location information and status data from SCPs 126 and prioritizesSCPs 126 based on the location information and the status data (202). NF121 transfers an NF request to NRF 125 (203). For example, NF 121 mayregister with NRF 125 and the registration may indicate an NF type thatNF 121 wants to establish communications with. NRF 125 receives the NFrequest from NF 121, and in response, generates and transfers a listthat prioritizes SCP 126 based on the location information to NF 121(204). NF 121 receives the list, selects one of SCPs 126 based on thelocation information and the status data, and transfers NF data to theselected one of SCPs 126 (205). The selected one of SCPs 126 receivesthe NF data and forwards the NF data to NF 123 (206). The processrepeats (207).

FIG. 3 illustrates an exemplary operation of wireless communicationnetwork 100 to exchange data communications through SCPs 126. Theoperation may vary in other examples. SCPs 126 determine locationinformation and status data for themselves. For example, the locationinformation may indicate geolocation and domain for the ones of SCPs 126and the status data may indicate the load and capacity of the ones ofSCPs 126. SCPs 126 register with NRF 125. During their registrations,SCPs 126 indicate their location information and status data to NRF 125.NRF 125 identifies the locations of SCPs 126 based on the locationinformation and prioritizes SCPs 126 based on the status data.

NF 121 registers with NRF 125. The NF registration indicates the NF typefor NF 121 and indicates the geolocation of NF 121. NRF 125 identifiesthe location of NF 121 and responsively generates an SCP list for NF121. The SCP list prioritizes SCPs 126 based on their location and theirstatus data. Typically, NRF 125 prioritizes SCPs that are proximate toNF 121 over SCPs that are distant from NF 121. Typically, NRF 125prioritizes lightly loaded SCPs over heavily loaded SCPs. Typically, NRF125 prioritizes SCPs that have higher capacity over SCPs that have lesscapacity. Typically, NRF 125 prioritizes SCPs that are proximate to therequesting NF over SCPs that are distant to the requesting NF. In someexamples, NRF 125 normalizes the proximity, load, capacity, and/or otherfactors indicated by the location information and status data into acombined score to prioritize SCPs 126. NRF 125 transfers the SCP list toNF 121.

NF 122 registers with NRF 125. The NF registration indicates the NF typeand geolocation of NF 122. NRF 125 identifies the location of NF 122 andresponsively generates an SCP list for NF 122. The SCP list prioritizesSCPs 126 for NF 122 based on the SCP locations status data and thelocation of NF 122. NRF 125 transfers the SCP list to NF 122. NF 123registers with NRF 125. The NF registration indicates the NF type andgeolocation of NF 123. NRF 125 identifies the location of NF 123 andresponsively generates an SCP list for NF 123. The SCP list prioritizesSCPs 126 for NF 123 based on the SCP locations status data and thelocation of NF 123. NRF 125 transfers the SCP list to NF 123. NF 124registers with NRF 125. The NF registration indicates the NF type andgeolocation of NF 124. NRF 125 identifies the location of NF 124 andresponsively generates an SCP list for NF 124. The SCP list prioritizesSCPs 126 for NF 124 based on the SCP locations status data and thelocation of NF 124. NRF 125 transfers the SCP list to NF 124.

NF 121 identifies a need to communicate with another NF. For example, NF121 may receive a service request from a wireless user device andresponsively identify a NF need to fulfil the service request. Inresponse, NF 121 selects one of SCPs 126 based on the locationinformation and status data indicated by the SCP list. NF 121 transfersNF data to the selected one of SCPs 126. The NF data indicates an NFtype. The selected one of SCPs 126 identifies the NF type in the NF dataand in response, selects NF 123 for NF 121. The selected one of SCPs 126transfers the NF data to NF 123 to establish communications between NF121 and NF 123.

SCPs 126 transfer status heartbeats to NRF 125. The status heartbeatsindicate updated status data and/or location information for the ones ofSCPs 126. The frequency that SCPs 126 transfer the status heartbeats maybe periodic, scheduled, semi-random, one-time, random, or some otherrate. NRF 125 reprioritizes SCPs 126 based on the updated locationinformation and status data. For example, the load of one of SCPs 126may have fallen and NRF 125 may raise the priority of that SCP. NRF 125transfers a new SCP list for NF 121 to NF 121, transfers a new SCP listfor NF 122 to NF 122, transfers a new SCP list for NF 123 to NF 123, andtransfers a new SCP list for NF 124 to NF 124.

NF 124 identifies a need to communicate with another NF. In response, NF124 selects one of SCPs 126 based on the new location information andnew status data indicated by the new SCP list. NF 124 transfers NF datato the selected one of SCPs 126. The NF data indicates an NF type. Theselected one of SCPs 126 identifies the NF type in the NF data and inresponse, selects NF 122 for NF 124. The selected one of SCPs 126transfers the NF data to NF 122 to establish communications between NF124 and NF 122.

FIG. 4 illustrates Fifth Generation (5G) communication network 400 toexchange data communications through Session Communication Proxies(SCPs) 421-423 and SCPs 441-443. 5G communication network 400 comprisesan example of wireless communication network 100, although network 100may differ. 5G network 400 comprises Region A and Region B. Region A andRegion B are typically different geographic areas, however the regionsmay comprise different network domains, Public Land Mobile Networks(PLMNs), Virtual Private Networks (VPNs), and the like. In Region A, 5Gnetwork 400 comprises Access and Mobility Management Function (AMF) 411,Session Management Function (SMF) 412, User Plane Function (UPF) 413,Authentication Server Function (AUSF) 414, Policy Control Function (PCF)415, Unified Data Management (UDM) 416, Network Repository Function(NRF) 417, and SCPs 421-423. In Region B, 5G network 400 comprises AMF431, SMF 432, UPF 433, AUSF 434, PCF 435, UDM 436, NRF 437, and SCPs441-443. Other network functions, network elements, and regions aretypically present in network 400 but are omitted for clarity.

In Region A, SCPs 421-423 register with NRF 417 and transferregistration information to NRF 417. The registration informationcomprises SCP addresses, SCP domains, SCP geolocations, SCP loads, SCPcapacities, and the like for individual ones of SCPs 421-423. NRF 417receives the registrations and responsively maintains SCP profiles forSCPs 421-423. The SCP profiles indicate an SCP Identifier (ID), SCPaddress, SCP geolocation, SCP domain, SCP load information, SCP capacityinformation, SCP capabilities and features, accessible end points,and/or other status data for individual ones of SCPs 421-423. NRF 417determines the number of available SCPs in Region A. For example, NRF417 may determine there are six active SCP instances in Region A. NRF417 transfers SCP update messages to NRF 437. The SCP update messagesindicate the SCP profiles for SCPs 421-423. NRF 437 maintains SCPprofiles for SCPs 421-423. NRF 437 determines the number of active SCPsessions in Region A.

In Region B, SCPs 441-443 register with NRF 437 and transferregistration information to NRF 437. The registration informationcomprises SCP addresses, SCP domains, SCP geolocations, SCP loads, SCPcapacities, and the like for individual ones of SCPs 441-443. NRF 437receives the registrations and responsively maintains SCP profiles forSCPs 441-443. The SCP profiles indicate an SCP Identifier (ID), SCPaddress, SCP geolocation, SCP load information, SCP capacityinformation, SCP capabilities and features, accessible end points,and/or other status data for individual ones of SCPs 441-443. NRF 437determines the number of available SCPs in Region B. NRF 437 transfersSCP update messages to NRF 417. The SCP update messages indicate the SCPprofiles for SCPs 441-443. NRF 417 maintains SCP profiles for SCPs441-443. NRF 417 determines the number of active SCP sessions in RegionB.

In Region A, NFs 411-416 register with NRF 417 and transfer registrationinformation to NRF 417. The registration information comprises NF ID, NFtype, NF address, NF geolocation, NF load, NF capacity, and the like forindividual ones of NFs 411-416. NRF 417 receives the registrations andresponsively maintains NF profiles for NFs 411-416. The NF profilesindicate the NF ID, NF type, NF address, NF geolocation, NF load, NFcapacity, and/or other status information for individual ones of NFs411-416. NRF 417 maintains NF group data that indicates the number ofactive sessions for each NF type. For example, the NF group data mayindicate there are three active AUSF sessions in Region A. NRF 417transfers registration update messages to NRF 437. The registrationupdate messages indicate the NF profiles and NF group data for NFs411-416. NRF 437 maintains NF profiles and NF group data for NFs411-416.

NRF 417 prioritizes SCPs 421-423 and SCPs 441-443 for individual ones ofNFs 411-416 based SCP ID, SCP address, SCP geolocation, SCP loadinformation, SCP capacity information, SCP capabilities and features,accessible end points, and/or other status data of SCPs 421-423 and SCPs441-443, and the geographic location of NFs 411-416. The SCP load maycomprise microprocessor load and the SCP capacity may comprise memoryoccupancy. Typically, NRF 417 prioritizes SCPs that are geographicallyclose to ones of NFs 411-416 over SCPs that are geographically furtherfrom NFs 411-416. Typically, NRF 417 prioritizes SCPs that have lowerload over SCPs that have higher load. Typically, NRF 417 prioritizesSCPs that have more capacity over SCPs that have less capacity. In someexamples, NRF 417 normalizes, weights, and combines the load, capacity,geolocation, and/or other factors for individual ones of SCPs into apriority score. NRF 417 generates prioritized lists of SCPs 421-423 and441-443 for NFs 411-416 based on the priority scores. The prioritizedlists rank SCPs 421-423 and 441-443 for NFs 411-416 and indicate theload, capacity, geolocation, and/or other status data for SCPs 421-423and 441-443. The prioritized lists may vary between NFs 411-416. Forexample, the prioritized SCP list for AMF 411 may rank SCP 421 over SCP422 while the prioritized list for AUSF 414 may rank SCP 422 over SCP421. NRF 417 transfers the prioritized SCP lists to NFs 411-416.

In Region B, NFs 431-436 register with NRF 437. NFs 431-436 transferregistration information to NRF 437. The registration informationcomprises NF ID, NF type, NF address, NF geolocation, NF load, NFcapacity, and the like for individual ones of NFs 431-436. NRF 437receives the registrations and responsively maintains NF profiles forNFs 431-436. The NF profiles indicate individual status for NFs 431-436and indicate the NF ID, NF type, NF address, NF geolocation, NF load, NFcapacity, and the like for individual ones of NFs 431-436. NRF 437maintains NF group data that indicates the number of active sessions foreach NF type. NRF 437 transfers registration update messages to NRF 417.The registration update messages indicate the NF profiles and NF groupdata for NFs 431-436. NRF 417 receives the registration update messagesand responsively maintains NF profiles and NF group data for NFs431-436.

NRF 437 prioritizes SCPs 421-423 and SCPs 441-443 for individual ones ofNFs 431-436 based on the load, capacity, geographic location of SCPs421-423 and SCPs 441-443, and the geographic location of NFs 431-436.The SCP load may comprise microprocessor load and the SCP capacity maycomprise memory occupancy. Typically, NRF 437 prioritizes SCPs that aregeographically close to ones of NFs 431-436 over SCPs that aregeographically further from NFs 431-436. Typically, NRF 437 prioritizesSCPs that have lower load over SCPs that have higher load. Typically,NRF 437 prioritizes SCPs that have more capacity over SCPs that haveless capacity. In some examples, NRF 437 normalizes the load, capacity,geolocation, and/or other factors for individual ones of SCPs 421-423and 441-443 into a score to prioritize SCPs 421-423 and 441-443 for NFs411-416. NRF 417 generates prioritized lists of SCPs 421-423 and 441-443for NFs 411-416 based on the prioritizations. The prioritized lists rankSCPs 421-423 and 441-443 for NFs 411-416 and indicate the load,capacity, geolocation, and/or other status data for SCPs 421-423 and441-443. The prioritized lists may vary between NFs 431-436. Forexample, the prioritized SCP list for SMF 432 may rank SCP 421 over SCP442 while the prioritized list for PCF 435 may rank SCP 442 over SCP421. NRF 417 transfers the prioritized SCP lists to NFs 411-416.

In Region A, NFs 411-416 identify a NF function need. For example, AMF411 may determine that is does not currently have access to an SMF thatcan serve a PDU a wireless user device. NFs 411-416 select ones of SCPs421-423 and 441-443 based on their SCP lists. For example, UDM 416 mayselect SCP 422 for communication based on the rank, proximity, load, andcapacity of SCP 422 indicated by the SCP list for UDM 416. NFs 411-416transfer NF discovery requests for NF types to their selected SCPs. Forexample, the NF discovery request may specify PCF as the NF type. SCPs421-423 and 441-443 identify the requested NF types in the NF discoveryrequests. SCPs 421-423 forward the NF discovery requests to therequested NF types. For example, AMF 411 may transfer an NF discoveryrequest for an AUSF to SCP 421, and SCP 421 may identify the NF type asAUSF and responsively route the NF discovery request to AUSF 414 or AUSF434. NFs 411-416 establish communications with the requested NF typesover SCPs 421-423 and 441-443. In Region B, NFs 431-436 may establishcommunications with other NFs over SCPs 421-423 and 441-443 in a similarmanner to NFs 411-416 in region A.

In Region A, SCPs 421-423 transfer status heartbeats to NRF 417. Thestatus heartbeats indicate updated SCP load, SCP capacity, and/or otherupdated SCP information for individual ones of SCPs 421-423. Thetransfer of the heartbeats may be periodic, scheduled, semi-random,one-time, random, or some other rate. NRF 417 receives the statusheartbeats and responsively updates the SCP profiles to indicate theupdated SCP load, SCP capacity, and/or other updated information forindividual ones of SCPs 421-423. NRF 417 updates the SCP group data inresponse to the status updates. For example, one of SCPs 421-423 maydeactivate during a maintenance period and NFR 417 may update the SCPgroup data to reflect this change. NRF 417 transfers status heartbeatmessages for SCPs 421-423 to NRF 437. The status heartbeat messagesindicate the updated SCP profiles and updated SCP group data for SCPs421-423. In response, NRF 437 updates the SCP profiles and SCP groupdata for SCPs 421-423.

In Region B, SCPs 441-443 transfer status heartbeats to NRF 437. Thestatus heartbeats indicate updated SCP load, SCP capacity, and/or otherupdated SCP information for individual ones of SCPs 441-443. Thetransfer of the heartbeats may be periodic, scheduled, semi-random,one-time, random, or some other rate. NRF 437 receives the statusupdates and responsively updates the SCP profiles to indicate theupdated SCP load, SCP capacity, and/or other updated information forindividual ones of SCPs 441-443. NRF 437 updates the SCP group data inresponse to the status updates. For example, one of SCPs 441-443 mayreactivate after the end of a maintenance period and NFR 437 may updatethe SCP group data to reflect this change. NRF 437 transfers statusheartbeat messages for SCPs 441-443 to NRF 417. The status heartbeatmessages indicate the updated SCP profiles and updated SCP group datafor SCPs 441-443. In response, NRF 417 updates the SCP profiles and SCPgroup data for SCPs 441-443.

In Region A, NRF 417 reprioritizes SCPs 421-423 and SCPs 441-443 forindividual ones of NFs 411-416 based on the updated load, updatedcapacity, updated location information, and/or other updated status dataindicated by the status heartbeats of SCPs 421-423 and SCPs 441-443, andthe geographic location of NFs 411-416. NRF 417 generates newprioritized lists of SCPs 421-423 and 441-443 for NFs 411-416 based onthe updated prioritizations. The new prioritized lists rank SCPs 421-423and 441-443 for NFs 411-416 and indicate the updated load, updatedcapacity, updated geolocation, and/or other updated status data for SCPs421-423 and 441-443. NRF 417 transfers the prioritized SCP lists to NFs411-416.

In Region B, NRF 437 reprioritizes SCPs 421-423 and SCPs 441-443 forindividual ones of NFs 431-436 based on the updated load, updatedcapacity, and updated location information of SCPs 421-423 and SCPs441-443, and the geographic location of NFs 431-436. NRF 437 generatesnew prioritized lists of SCPs 421-423 and 441-443 for NFs 431-436 basedon the updated prioritizations. The new prioritized lists rank SCPs421-423 and 441-443 for NFs 431-436 and indicate the updated load,updated capacity, updated geolocation, and/or other updated status datafor SCPs 421-423 and 441-443. NRF 437 transfers the prioritized SCPlists to NFs 431-436.

In Region A, NFs 411-416 identify another NF function need. For example,AMF 411 may determine that is does not currently have access to an AUSFto authenticate a wireless user device. NFs 411-416 select ones of SCPs421-423 and 441-443 based on their updated SCP lists. For example, SMF412 may have previously selected SCP 421 and subsequently selects SCP422 for communication based on the updated rank, updated proximity,updated load, and updated capacity of SCP 422 as indicated by the SCPlist for SMF 412. NFs 411-416 transfer NF discovery requests for NFtypes to their selected SCPs. SCPs 421-423 and 441-443 identify therequested NF types in the NF discovery requests and forward the NFdiscovery requests to the requested NF types. NFs 411-416 establishcommunications with the requested NF types over SCPs 421-423 and441-443. In Region B, NFs 431-436 may establish communications withother NFs over SCPs 421-423 and 441-443 in a similar manner to NFs411-416 in region A.

In some examples, NRFs 417 and 437 hide individual ones of SCPs 421-423and 441-443 from discovery by NFs 411-416 and NFs 431-436. NRF 417retrieves SCP profiles and SCP group data for SCPs 421-423 and 441-443and determines the SCP geolocation, SCP load, SCP capacity, and thenumber of active SCP instances. NRF 417 determines an SCP performancethreshold. NRF 417 determines when individual ones of SCPs 421-423 and441-443 fall below the performance threshold. For example, NRF 417 maydetermine the load for one of SCP 443 is below the performance thresholdand NRF 417 may responsively remove SCP 443 from the prioritized SCPlists for NFs 421-423 and 441-443. NRF 417 does not indicate hidden onesof SCPs 421-423 and 441-443 to NFs 411-416 to prevent the NFs 411-416from establishing communications over the hidden SCP. In Region B, NRF437 may hide SCPs 421-423 and 441-443 in a similar manner as NRF 417.

In some examples, NRFs 417 and 437 load balance the prioritization ofSCPs 421-423 and 441-443. NRF 417 receives registration requests fromNFs 411-416. NRF 417 retrieves SCP profiles and SCP group data for SCPs421-423 and 441-443. NRF 417 load-balances the priority of SCPs 421-423and 441-443. For example, NRF 417 may generate and transfer SCP lists toNFs 411-416 that give the highest priority to SCPs 421-423 and 441-443in a proportional manner so that SCPs 421-423 and 441-443 are selectedby NFs 411-416 in an equal manner. Typically, NRF 417 prioritizes SCPs421-423 and 441-443 to distribute SCP usage across the 5G core 410 andto prevent any one SCP from becoming overused. In Region B, NRF 437 mayload balance the priority of SCPs 421-423 and 441-443 in a similarmanner as NRF 417.

FIG. 5 illustrates Network Function Virtualization Infrastructure (NFVI)500 and NFVI 600. NFVI 500 and NFVI 600 comprise an example of networkfunctions 121-126, although functions 121-126 may vary from thisexample. NFVI 500 comprises NFVI hardware 501, NFVI hardware drivers502, NFVI operating systems 503, NFVI virtual layer 504, and NFVIVirtual Network Functions (VNFs) 505. NFVI hardware 501 comprisesNetwork Interface Cards (NICs), CPU, RAM, Flash/Disk Drives (DRIVE), andData Switches (SW). NFVI hardware drivers 502 comprise software that isresident in the NIC, CPU, RAM, DRIVE, and SW. NFVI operating systems 503comprise kernels, modules, applications, containers, hypervisors, andthe like. NFVI virtual layer 504 comprises vNIC, vCPU, vRAM, vDRIVE, andvSW. NFVI VNFs 505 comprise AMF 511, SMF 512, UPF 513, AUSF 514, PCF515, UDM 516, NRF 517, and SCPs 521-523. Additional VNFs and networkelements like Network Slice Selection Function (NSSF), Unified DataRegistry (UDR), and Network Exposure Function (NEF) are typicallypresent but are omitted for clarity. NFVI 500 may be located at a singlesite or be distributed across multiple geographic locations. The NIC inNFVI hardware 501 is coupled to a NIC in NFVI hardware 601 and toexternal systems. NFVI hardware 501 executes NFVI hardware drivers 502,NFVI operating systems 503, NFVI virtual layer 504, and NFVI VNFs 505 toform AMF 411, SMF 412, UPF 413, AUSF 414, PCF 415, UDM 416, NRF 417, andSCPs 421-423.

In a like manner, NFVI 600 comprises NFVI hardware 601, NFVI hardwaredrivers 602, NFVI operating systems 603, NFVI virtual layer 604, andNFVI VNFs 605. NFVI hardware 601 comprises NICs, CPU, RAM, DRIVE, andSW. NFVI hardware drivers 602 comprise software that is resident in theNIC, CPU, RAM, DRIVE, and SW. NFVI operating systems 603 comprisekernels, modules, applications, containers, hypervisors, and the like.NFVI virtual layer 604 comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. NFVIVNFs 605 comprise AMF 631, SMF 632, UPF 633, AUSF 634, PCF 635, UDM 636,NRF 637, and SCPs 641-643. Additional VNFs and network elements aretypically present but are omitted for clarity. NFVI 600 may be locatedat a single site or be distributed across multiple geographic locations.The NIC in NFVI hardware 600 is coupled to a NIC in NFVI hardware 501and to external systems. NFVI hardware 601 executes NFVI hardwaredrivers 602, NFVI operating systems 603, NFVI virtual layer 604, andNFVI VNFs 605 to form AMF 431, SMF 432, UPF 433, AUSF 434, PCF 435, UDM436, NRF 437, and SCPs 441-443. In some examples, NFVI 500 and NFVI 600are integrated into a signal NFVI that executes to from the networkfunctions and network elements in Region A and Region B of 5G core 410.

FIG. 6 further illustrates NFVI 500 and NFVI 600 in 5G communicationnetwork 400. AMPs 411 and 431 perform UE registration and connection, UEconnection/mobility management, and UE authentication and authorization.SMFs 412 and 432 perform session establishment and management, UPFselection and control, network address allocation, and N1 termination.UPFs 413 and 433 perform packet routing & forwarding, packet inspection,QoS handling, PDU interconnection, and mobility anchoring. AUSFs 424 and434 perform UE access authentication. PCFs 425 and 435 perform networkrules management and distribution and network subscription policymanagement. UDMs 416 and 436 perform LIE subscription management and keygeneration. NRFs 417 and 437 perform network function discovery, networkfunction profile management, SCP prioritization. SCPs 421-423 and441-443 perform indirect communication, location and statustransferring, and location and status heartbeat transferring.

In this example, AMF 411 establishes communications with other NFsthrough SCPs 421-423 and 441-443, however the operation may vary inother examples. SCPs 421-423 register with NRF 417 and indicate theirSCP addresses, SCP domains, SCP geolocations, SCP loads, SCP capacities,and the like for individual ones of SCPs 421-423. The SCP loads maycomprise microprocessor occupancy, Input/Output percent, and/or memoryoccupancy. NRF 417 receives the registrations and responsively maintainsSCP profiles for SCPs 421-423. The SCP profiles indicate an SCP IDs, SCPaddresses, SCP geolocations, SCP domains, SCP load information, SCPcapacity information, accessible end points, and/or other status datafor individual ones of SCPs 421-423. NRF 417 identifies the amount ofavailable SCPs in Region A. NRF 417 transfers SCP update messages to NRF437. The SCP update messages indicate the SCP profiles for SCPs 421-423.NRF 437 maintains SCP profiles for SCPs 421-423 and identifies theamount of active SCP sessions in Region A.

SCPs 441-443 register with NRF 437 and indicate their SCP addresses, SCPdomains, SCP geolocations, SCP loads, SCP capacities, and the like forindividual ones of SCPs 441-443. NRF 437 receives the registrations andresponsively maintains SCP profiles for SCPs 441-443 that indicate SCPIDs, SCP addresses, SCP geolocations, SCP load information, SCP capacityinformation, accessible end points, and/or other status data forindividual ones of SCPs 441-443. NRF 437 identifies the amount ofavailable SCPs in Region B. NRF 437 transfers SCP update messages to NRF417 that indicate the SCP profiles for SCPs 441-443. NRF 417 maintainsSCP profiles for SCPs 441-443. NRF 417 determines the number of activeSCP sessions in Region B.

AMF 411 registers with NRF 417. AMF 411 indicates its NF ID, NF type, NFaddress, NF geolocation, NF load, NF capacity, and the like to NRF 417.NRF 417 receives the registration and responsively creates an NF profilefor AMF 411. The NF profiles indicate the NF ID, NF type, NF address, NFgeolocation, NF load, NF capacity, and/or other status information forAMF 411. NRF 417 transfers a registration update message to NRF 437 thatindicates the NF profile for AMF 411 and NF group data for NFs 411-416.NRF 437 maintains NF profiles and NF group data for NFs 411-416.

NRF 417 prioritizes SCPs 421-423 and SCPs 441-443 for AMF 411 based onthe load, capacity, geographic location of SCPs 421-423 and SCPs441-443, and the geographic location of AMF 411. NRF 417 prioritizesSCPs that are geographically close to ones AMF 411 over SCPs that aregeographically distant from AMF 411. NRF 417 prioritizes SCPs that havelower load over SCPs that have higher load. NRF 417 prioritizes SCPsthat have more capacity over SCPs that have less capacity. NRF 417normalizes the load, capacity, geolocation, and/or other factors forindividual ones of SCPs 421-423 and 441-443 into scores to prioritizeSCPs 421-423 and 441-443 for AMF 411. NRF 417 generates prioritizedlists of SCPs 421-423 and 441-443 for AMF 411 that ranks SCPs 421-423and 441-443 for AMF 411 and that indicates the load, capacity,geolocation, and/or other status data for SCPs 421-423 and 441-443. NRF417 transfers the prioritized SCP list to AMF 411. In some examples, NRF417 may load balances the priority of SCPs 421-423 and 441-443 todistribute NF usage of the SCPs. NRF 437 may prioritize SCPs 421-423 and441-443 in a similar manner to NRF 417.

AMF 411 identifies an NF function need for a UDM. For example, AMF 411may determine that it needs access to a UDM to retrieve context for awireless user device. AMF 411 selects ones of SCP 421 based on thepriority, geolocation, load, and capacity for SCP 421 indicated by theSCP list. AMF 411 transfers an NF discovery request for a UDM to SCP421. SCPs 421 identifies the requested NF types as UDM and responsivelyselects UDM 416 to establish communication. In other examples, SCP 421may instead select UDM 437 when SCP 421 can access UDM 437. SCP forwardsthe NF discovery requests to UDM 416. UDM 416 accepts the NF discoveryrequest and transfers an indication to AMF 411. AMF 411 communicationswith UDM 416. In NFs 412-416 and 431-436 may establish communicationswith other NFs over SCPs 421-423 and 441-443 in a similar manner to AMF411.

SCPs 421-423 transfer status heartbeats to NRF 417 that indicate updatedSCP load, SCP capacity, and/or other updated SCP information forindividual ones of SCPs 421-423. For example, the load of SCP 421 mayhave increased, and SCP 421 may indicate this to NRF 417 in the statusheartbeat. NRF 417 receives the status updates and responsively updatesthe SCP profiles to indicate the updated SCP load, SCP capacity, and/orother updated information for individual ones of SCPs 421-423. NRF 417updates the SCP group data in response to the status updates NRF 417transfers status heartbeat messages for SCPs 421-423 to NRF 437 thatindicate the updated SCP profiles and updated SCP group data for SCPs421-423. In response, NRF 437 updates the SCP profiles and SCP groupdata for SCPs 421-423.

SCPs 441-443 transfer status heartbeats to NRF 437 that indicate updatedSCP load, SCP capacity, and/or other updated SCP information forindividual ones of SCPs 441-443. NRF 437 receives the status updates andresponsively updates the SCP profiles to indicate the updated SCP load,SCP capacity, and/or other updated information for individual ones ofSCPs 441-443. NRF 437 updates the SCP group data in response to thestatus updates. NRF 437 transfers status heartbeat messages for SCPs441-443 to NRF 417. The status heartbeat messages indicate the updatedSCP profiles and updated SCP group data for SCPs 441-443. In response,NRF 417 updates the SCP profiles and SCP group data for SCPs 441-443.

NRF 417 reprioritizes SCPs 421-423 and SCPs 441-443 for AMF 411 based onthe updated load, updated capacity, updated location information, andthe geographic location of AMF 411. NRF 417 generates new prioritizedlists of SCPs 421-423 and 441-443 for AMF 411 based on the updatedprioritizations. The new prioritized lists rank SCPs 421-423 and 441-443for NFs 411-416 and indicate the updated load, updated capacity, updatedgeolocation, and/or other updated status data for SCPs 421-423 and441-443. NRF 417 transfers the new prioritized SCP list to AMF 411.

AMF 411 identifies a need for an AUSF. For example, AMF 411 maydetermine that is does not currently have access to an AUSF toauthenticate a wireless user device. AMF 411 selects ones of SCP 442based on updated load, updated capacity, and/or other updatedinformation for SCP 442 indicated by the new SCP list. AMF 411 transfersan NF discovery request for AUSF to SCP 442. SCP 442 identifies therequested NF type in the NF discovery request as AUSF and responsivelyselects AUSF 434 for AMF 411. SCP 442 forwards the NF discovery requestto AUSF 434. AUSF 434 accepts the NF discovery request and responsivelytransfers an indication to AMF 411. AMF 411 establish communicationswith the requested with AUSF 434.

FIG. 7 illustrates NRFs 417 and 437 and SCPs 421-423 and 441-443 in 5Gcommunication network 400. NRFs 417 and 437 comprise examples of NRF125, although NRF 125 may differ. SCPs 421-423 and 441-443 transfertheir addresses, loads, and locations to NRFs 417 and 437 during SCPregistration. Once registered, SCPs 421-423 and 441-443 transfer statusheartbeats that indicate updated addresses, updated loads, and updatedlocations to NRFs 417 and 437. NRFs 417 and 437 comprise registrationcomponents that interact with SCPs 421-423 and 441-443 to obtain SCPstatus data and SCP location information and that interact with NFs411-416 and 431-436 to obtain NF locations and NF addresses. NRFs 417and 437 comprise select/prioritize components that select SCP addressesand prioritize the selected SCP addresses based on SCP load, SCPlocation, and NF location. Lightly loaded SCPs are typically given ahigher priority than heavily loaded SCPs. Geographically closer SCPs aretypically given a higher priority than geographically further SCPs.Load, location, and SCP other factors may be normalized and combinedinto a common SCP priority score.

FIG. 8 illustrates an exemplary operation of the 5G communicationnetwork to exchange data communications through SCPs 421-423 and441-443. The operation may vary in other examples. In this example, AMF411 discovers a UDM and PCF through SCP 421 to serve User Equipment (UE)801 and SMF 412 discovers a UDM through SCP 422 to serve UE 801, howeverthe operation may differ in other examples.

In Region A, SCPs 421-423 register with NRF 417. NRF 417 receives theregistrations and responsively maintains SCP profiles for SCPs 421-423that indicate SCP ID, SCP address, SCP geolocation, SCP domain, SCP loadinformation, SCP capacity information, accessible end points, and/orother status data for individual ones of SCPs 421-423. NRF 417 transfersSCP update messages to NRF 437. NRF 437 receives the update messages andresponsively maintains SCP profiles for SCPs 421-423. In Region B, SCPs441-443 register with NRF 437. NRF 437 receives the registrations andresponsively maintains SCP profiles for SCPs 441-443 that indicate SCPID, SCP address, SCP geolocation, SCP domain, SCP load information, SCPcapacity information, accessible end points, and/or other status datafor individual ones of SCPs 441-443. NRF 437 transfers SCP updatemessages to NRF 417. NRF 417 receives the update messages andresponsively maintains SCP profiles for SCPs 441-443.

AMF 411 and SMF 412 register with NRF 417. The registrations indicate NFIDs, NF types, NF addresses, NF geolocations, NF loads, NF capacities,and the like for AMF 411 and SMF 412. NRF 417 responsively maintains NFprofiles for AMF 411 and SMF 412 that indicate the NF IDs, NF types, NFaddresses, NF geolocations, NF loads, NF capacities, and/or other statusinformation. NRF 417 transfers registration update messages to NRF 437.The registration update messages indicate the NF profiles for AMF 411and SMF 412. NRF 437 maintains NF profiles for AMF 411 and SMF 412.

NRF 417 prioritizes SCPs 421-423 and SCPs 441-443 for AMF 411 based onthe load, capacity, geographic location of SCPs 421-423 and SCPs441-443, and the geographic location of AMF 411. NRF 417 prioritizesSCPs 421-423 and SCPs 441-443 for SMF 412 based on the load, capacity,geographic location of SCPs 421-423 and SCPs 441-443, and the geographiclocation of SMF 412. NRF 417 normalizes the load, capacity, geolocation,and/or other factors for individual ones of SCPs 421-423 and 441-443into a score to prioritize SCPs 421-423 and 441-443 for AMF 411 and forSMF 412. NRF 417 generates a prioritized list of SCPs 421-423 and441-443 for AMF 411 based on the SCP prioritization for AMF 411. NRF 417generates a prioritized list of SCPs 421-423 and 441-443 for SMF 412based on the SCP prioritization for SMF 412. The prioritized SCP listfor AMF 411 gives highest priority to SCP 421. The prioritized SCP listfor SMF 412 gives highest priority to SCP 423. NRF 417 transfers theprioritized SCP lists to AMF 411 and SMF 412.

UE 801 attaches to AMF 411 over access node 811. UE 801 transfers aregistration request to AMF 411. AMF 411 receives the registrationrequest from UE 801. AMF 411 transfers an authentication request for UE801 to AUSF 414. AUSF 414 interacts with UDM 416 to authenticate UE 801and upon authentication, indicates the authentication to AMF 411. AMF411 interacts with other network functions to authorize UE 801 fornetwork service. Responsive to the authentication and authorization, AMF411 identifies a UDM function need to retrieve UE context for UE 801.AMF 411 selects SCP 421 to establish communications with a UDM based onthe priority, proximity, domain, and load of SCP 421 indicated by theSCP list. AMF 411 transfers an NF discovery requests for a UDM to SCP421. SCPs 421 identifies UDM 416 and forwards the NF discovery requeststo UDM 416. UDM 416 transfers a response to AMF 411 to establishcommunications. AMF 411 retrieves UE context for UE 801 from UDM 416.The UE context comprises QoS, slice IDs, network addresses, and thelike. AMF 411 transfers the UE context to UE 801.

In Region A, SCPs 421-423 transfer status heartbeats to NRF 417. NRF 417receives the status heartbeats and responsively updates the SCP profilesto indicate updated SCP load, SCP capacity, and/or other updatedinformation for individual ones of SCPs 421-423. NRF 417 transfersstatus heartbeat messages for SCPs 421-423 to NRF 437. The statusheartbeat messages indicate the updated SCP profiles for SCPs 421-423.In response, NRF 437 updates the SCP profiles for SCPs 421-423. InRegion B, SCPs 441-443 transfer status heartbeats to NRF 437. NRF 437receives the status heartbeats and responsively updates the SCP profilesto indicate updated SCP load, SCP capacity, and/or other updatedinformation for individual ones of SCPs 441-443. NRF 437 transfersstatus heartbeat messages for SCPs 441-443 to NRF 417. The statusheartbeat messages indicate the updated SCP profiles for SCPs 441-443.In response, NRF 417 updates the SCP profiles for SCPs 441-443.

NRF 417 reprioritizes SCPs 421-423 and SCPs 441-443 for AMF 411 based onthe updated load, updated capacity, updated geographic location of SCPs421-423 and SCPs 441-443, and the geographic location of AMF 411. NRF417 reprioritizes SCPs 421-423 and SCPs 441-443 for SMF 412 based on theupdated load, updated capacity, updated geographic location of SCPs421-423 and SCPs 441-443, and the geographic location of SMF 412. NRF417 normalizes the updated load, capacity, geolocation, and/or otherfactors for individual ones of SCPs 421-423 and 441-443 into a new scoreto reprioritize SCPs 421-423 and 441-443 for AMF 411 and for SMF 412.NRF 417 generates a new prioritized list of SCPs 421-423 and 441-443 forAMF 411 based on the SCP prioritization for AMF 411. NRF 417 generates anew prioritized list of SCPs 421-423 and 441-443 for SMF 412 based onthe SCP prioritization for SMF 412. The new prioritized SCP list for AMF411 gives highest priority to SCP 421. The prioritized SCP list for SMF412 gives highest priority to SCP 422. NRF 417 transfers the prioritizedSCP lists to AMF 411 and SMF 412.

A user application in UE 801 executes and UE 801 responsively transfersa Protocol Data Unit (PDU) session request to AMF 411. AMF 411 directsthe SMF 412 to establish the PDU session for UE 801. SMF 412 identifiesa UDM need to retrieve UE context for UE 801 for the PDU session. SMFselects SCPs 422 based on their updated rank, updated proximity, updatedload, and updated capacity of SCP 422 as indicated by the SCP list forSMF 412. Although SCP 422 was indicated with the highest priority, insome examples SMF 412 may select a lower priority SCP when certainprerequisites are met. SMF 412 transfers NF discovery requests for a UDMto SCP 422. SCP 422 identifies the requested NF types as UDM. SCP 422selects UDM 416 for SMF 412. SCP 422 forwards the NF discovery requestto UDM 416. UDM 416 accepts the discovery request and SMF 412 establishcommunications with UDM 416. SMF 412 retrieves UE context for UE 801 toestablish the PDU session and selects UPF 413 to serve the PDU sessionto UE 801. SMF 412 transfers session context for the PDU session to AMF411. AMF 411 indicates the session context to UE 801. UE 801 uses thesession context to establish the PDU session. UE 801 exchanges user datafor the PDU session with UPF 413. UPF 413 exchanges the user data withdata network 821.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose network circuitry toexchange data communications through Session Communication Proxies(SCPs). The computer hardware comprises processing circuitry like CPUs,DSPs, GPUs, transceivers, bus circuitry, and memory. To form thesecomputer hardware structures, semiconductors like silicon or germaniumare positively and negatively doped to form transistors. The dopingcomprises ions like boron or phosphorus that are embedded within thesemiconductor material. The transistors and other electronic structureslike capacitors and resistors are arranged and metallically connectedwithin the semiconductor to form devices like logic circuitry andstorage registers. The logic circuitry and storage registers arearranged to form larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose network circuitry toexchange data communications through SCPs.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method to transfer data from an Access and Mobility Management Function (AMF) to a target network function, the method comprising: Session Communication Proxies (SCPs) generating SCP status information and SCP location information; a Network Repository Function (NRF) receiving the SCP status information and the SCP location information; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information; the NRF indicating the SCP prioritization to the AMF; the AMF selecting one of the SCPs based on the SCP prioritization; the AMF transferring the data to the selected one of the SCPs; and the selected one of the SCPs receiving the data, selecting the target network function, and transferring the data to the target network function.
 2. The method of claim 1 wherein: the SCPs generating the SCP status information and the SCP location information comprises indicating network domains for the SCPs; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises prioritizing the SCPs based on the network domains for the SCPs; and the AMF selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the prioritization based on the network domains for the SCPs.
 3. The method of claim 1 wherein: the SCPs generating the SCP status information and the SCP location information comprises indicating microprocessor status for the SCPs; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises prioritizing the SCPs based on the microprocessor status for the SCPs; and the AMF selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the prioritization based on the microprocessor status for the SCPs.
 4. The method of claim 1 wherein: the SCPs generating the SCP status information and the SCP location information comprises indicating memory status for the SCPs; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises prioritizing the SCPs based on the microprocessor status for the SCPs; and the AMF selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the SCP prioritization based on the memory status for the SCPs.
 5. The method of claim 1 wherein: the SCPs generating the SCP status information and the SCP location information comprises indicating Input/Output (I/O) status for the SCPs; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises prioritizing the SCPs based on the Input/Output (I/O) status for the SCPs; and the AMF selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the SCP prioritization based on the I/O status for the SCPs.
 6. The method of claim 1 wherein: the SCPs generating the SCP status information and the SCP location information comprises generating heartbeat signals for the SCPs; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises prioritizing the SCPs based on the heartbeat signals for the SCPs; and the AMF selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the SCP prioritization based on the heartbeat signals for the SCPs.
 7. The method of claim 1 wherein the target network function comprises one of a Session Management Function (SMF), Authentication Server Function (AUSF), a Unified Data Management (UDM), or a Policy Control Function (PCF).
 8. A method to transfer data from a source network function to a target network function, the method comprising: Session Communication Proxies (SCPs) generating SCP status information and SCP location information; a Network Repository Function (NRF) receiving the SCP status information and SCP location information; the NRF prioritizing the SCPs based on the SCP status information and the SCP location information; the NRF indicating the SCP prioritization to the source network function; the source network function selecting one of the SCPs based on the SCP prioritization; the source network function transferring the data to the selected one of the SCPs; and the selected one of the SCPs receiving the data, selecting the target network function, and transferring the data to the target network function.
 9. The method of claim 8 wherein: the NRF prioritizing the SCPs based on the SCP status information and the SCP location information comprises the NRF prioritizing the SCPs based on source network function proximity to the SCPs; and the source network function selecting the one of the SCPs based on the SCP prioritization comprises selecting the one of the SCPs using the SCP prioritization based on the source network function proximity to the selected one of the SCPs.
 10. The method of claim 8 wherein the source network function comprises an Access and Mobility Management Function (AMF).
 11. The method of claim 8 wherein the target network function comprises a Unified Data Management (UDM).
 12. The method of claim 8 wherein the target network function comprises an Authentication Server Function (AUSF).
 13. The method of claim 8 wherein the target network function comprises a Policy Control Function (PCF).
 14. The method of claim 8 wherein the target network function comprises a Session Management Function (SMF).
 15. A data communication system to transfer data from a source network function to a target network function, the data communication system comprising: Session Communication Proxies (SCPs) to generate SCP status information and SCP location information; a Network Repository Function (NRF) to receive the SCP status information and the SCP location information; the NRF to prioritize the SCPs based on the SCP status information and the SCP location information; the NRF to indicate the SCP prioritization to the source network function; the source network function to select one of the SCPs based on the SCP prioritization; the source network function to transfer the data to the selected one of the SCPs; and the selected one of the SCPs to receive the data, select the target network function, and transfer the data to the target network function.
 16. The data communication system of claim 15 wherein: the NRF to prioritize the SCPs based on the source network function proximity to the SCPs; the source network function is to select the one of the SCPs using the SCP prioritization based on the source network function proximity to the selected one of the SCPs.
 17. The data communication system of claim 15 wherein: the source network function comprises an Access and Mobility Management Function (AMF); and the target network function comprises one of a Unified Data Management (UDM), Authentication Server Function (AUSF), and a Policy Control Function (PCF).
 18. The data communication system of claim 15 wherein the SCP status information comprises microprocessor status for the SCPs.
 19. The data communication system of claim 15 wherein the SCP status information comprises memory status for the SCPs.
 20. The data communication system of claim 15 wherein source network function comprises an Access and Mobility Management Function (AMF) and the target network function comprises a Session Management Function (SMF). 